Web-enabled configurable quality data collection tool

ABSTRACT

A method and system for configuring trigger parameters for captured test fleet vehicle data collection. The method includes selecting at least one vehicle identifier from a captured test fleet database, associating at least one trigger condition with the at least one selected vehicle identifier in the database, associating at least one vehicle parameter to be collected at an occurrence of the at least one associated trigger condition with the selected vehicle identifier in the database, and sending the at least one associated trigger condition and the at least one associated vehicle parameter from the database to a telematics unit of at least one test vehicle associated with the vehicle identifier via a wireless connection.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Ser. No. 10/949,787 filedSep. 24, 2004, which claims priority of U.S. Provisional ApplicationSer. No. 60/509,606 filed Oct. 8, 2003. The entirety of each applicationis hereby incorporated by reference.

FIELD OF THE INVENTION

The invention relates to vehicle design and manufacture, and moreparticularly to methods and systems for a web-enabled configurablequality data collection tool for a vehicle in a captured test fleet.

BACKGROUND OF THE INVENTION

Vehicle design and manufacture typically includes an iterativedevelopment process to refine vehicle design parameters with eachsuccessive design. Various techniques are employed in the development ofa new vehicle, including the building and testing of pilot vehicles. Apilot vehicle is usually a limited manufacturing run of a reasonablymature or even pre-production vehicle design. The pilot vehicle isfrequently field tested in order to further refine the final productionvehicle prior to large scale manufacture. However, present vehiclemanufacturing technologies also allow for the ongoing refinement ofproduction vehicles through iterative development since automatedmanufacturing facilities operating just-in-time assembly processestypically do not require major retooling or down-time to accommodatedesign changes.

Field testing of a pilot or production vehicle typically involvesoperating the vehicle in a simulated or real-world driving environment,and collecting various vehicle system test and diagnostic data for laterreview and analysis. In a pilot vehicle, raw vehicle testing data istypically collected and stored in a field data collection apparatuswhile the vehicle is in operation. A diagnostic system is later pluggedinto the field data collection apparatus to download the raw testingdata after the completion of the vehicle field testing. Several vehiclesystems may be monitored during a vehicle field test, with thesubsequent data stored to the data collection apparatus. However, thecollected system data is limited to the data stored during the fieldoperation, and the data is not available in real-time to a diagnosticsystem. For vehicle field tests performed with this system, a staff isrequired to run the field test, and to retrieve the test data from thecollection apparatus. Each test vehicle must be individually downloadedof test data by a staff member plugging the data collection apparatusinto a diagnostic system or a secondary data storage medium. It istherefore impractical to collect data from more than a nominal number ofvehicles of a particular model during a fixed duration field testexercise. Additionally, while it is possible to integrate limited datacollection components into a production vehicle, the test data may onlybe collected from a production vehicle each time the vehicle visits afacility where the test data may be downloaded; for example, an autodealership. Moreover, an administrator trained specifically in how toread and decode the data must access the test data download.Furthermore, production vehicles having integrated data collectioncomponents will generally be limited in storage and processing power dueto increased costs of providing the data collection components, andtherefore the collection components may not have enough capacity tocollect data for a meaningful period between downloads, or mayexperience a data overflow prior to collecting statistically usefuldata. Iterative vehicle design enhancement is then hindered by theinability to collect statistically relevant quantities of test data froma large number of vehicles of a selected model. The inability to monitorcollected data in real-time, or on production vehicles further preventsan interactive design process across a large sample group.

It would be desirable therefore to provide a method and system forinteractive vehicle design and manufacture that overcomes these andother disadvantages.

SUMMARY OF THE INVENTION

In accordance with one aspect of the invention, a method of configuringvia the Internet trigger parameters for captured test fleet vehicle datacollection describes selecting at least one vehicle identifier from acaptured test fleet database, associating at least one trigger conditionwith the at least one selected vehicle identifier in the database,associating at least one vehicle parameter to be collected at anoccurrence of the at least one associated trigger condition with theselected vehicle identifier in the database, and sending the at leastone associated trigger condition and the at least one associated vehicleparameter from the database to a telematics unit of at least one testvehicle associated with the vehicle identifier via a wirelessconnection.

In accordance with another aspect of the invention, a computer readablemedium includes computer readable code for selecting at least onevehicle identifier from a captured test fleet database, computerreadable code for associating at least one trigger condition with theselected vehicle identifier in the database, computer readable code forassociating at least one vehicle parameter to be collected at anoccurrence of the at least one associated trigger condition with theselected vehicle identifier in the database, and computer readable codefor sending the at least one associated trigger condition and the atleast one associated vehicle parameter from the database to a telematicsunit of at least one test vehicle associated with the vehicle identifiervia a wireless connection.

In accordance with another aspect of the invention a system forconfiguring trigger parameters for captured test fleet vehicle datacollection, includes means for selecting at least one vehicle identifierfrom a captured test fleet database, means for associating at least onetrigger condition with the selected vehicle identifier in the database,means for associating at least one vehicle parameter to be collected atan occurrence of the at least one associated trigger condition with theselected vehicle identifier in the database, and means for sending theat least one associated trigger condition and the at least oneassociated vehicle parameter from the database to a telematics unit ofat least one test vehicle associated with the vehicle identifier via awireless connection.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustrative operating environment for a captured testfleet in an embodiment of the present invention;

FIG. 2 is a block diagram of an illustrative operating environment forinteractive vehicle design in accordance with an embodiment of thepresent invention;

FIG. 3 is a block diagram of a captured test fleet database inaccordance with an embodiment of the present invention;

FIG. 4 is a process flow diagram of a method for interactive design andmanufacture of a vehicle in accordance with an embodiment of the presentinvention;

FIG. 5 is a process flow diagram of a method for providing captured testfleet data from a test vehicle in accordance with an embodiment of thepresent invention;

FIG. 6 is a process flow diagram of a method for managing captured testfleet data in accordance with an embodiment of the present invention;

FIG. 7 is a process flow diagram of a method of obtaining captured testfleet data for vehicle design in accordance with an embodiment of thepresent invention;

FIG. 8 is a process flow diagram of a method for real-time wirelessinteractive test vehicle data collection in accordance with anembodiment of the present invention;

FIG. 9 is a block diagram of an illustrative operating environment forweb-enabled configurable quality data collection tool in accordance withan embodiment of the present invention;

FIG. 10 is a process flow diagram of a method for remote configurationof test vehicle data capture in accordance with an embodiment of thepresent invention; and

FIG. 11 is an example of a web-enabled client interface for data captureconfiguration for a test vehicle in a captured vehicle fleet inaccordance with an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENT

FIG. 1 is an illustrative operating environment for a captured testfleet in an embodiment of the present invention. In one embodiment, acaptured test fleet is comprised of a set of identified vehiclesmonitored for vehicle or vehicle component behavior. FIG. 1 shows acaptured test fleet vehicle communication system 100. Captured testfleet communication system 100 includes at least one captured testvehicle 110 (test vehicle, pilot vehicle, production vehicle) includingvehicle communication bus 112 and telematics unit 120, one or morewireless carrier systems 140, one or more communication networks 142,one or more land networks 144, one or more client, personal or usercomputers 150, one or more web-hosting portals 160, and one or more callcenters 170. In one embodiment, captured test vehicle 110 is implementedas a mobile vehicle equipped with suitable hardware and software fortransmitting and receiving voice and data communications.

In one embodiment, telematics unit 120 is a vehicle communications unitthat includes a processor 122 connected to a wireless modem 124, aglobal positioning system (GPS) unit 126, an in-vehicle memory 128, suchas, for example, a non-volatile flash memory, a microphone 130, one ormore speakers 132, an embedded or in-vehicle mobile phone 134, and awireless access point node 136. Processor 122 is also referred to as amicrocontroller, controller, host processor, or vehicle communicationsprocessor. GPS unit 126 provides longitude and latitude coordinates ofthe vehicle, as well as a time stamp. In-vehicle mobile telephone system134 is a cellular-type phone, such as, for example an analog, digital,dual-mode, dual-band, multi-mode or multi-band cellular phone. Inanother example, the mobile telephone system is an analog mobiletelephone system operating over a prescribed band nominally at 800 MHz.In another example, the mobile telephone system is a digital mobiletelephone system operating over a prescribed band nominally at 800 MHz,900 MHz, 1900 MHz, or any suitable band capable of carrying digitalcellular communications.

Processor 122 executes various computer programs and communicationcontrol and protocol algorithms that control communication, programming,and operational modes of electronic and mechanical systems within testvehicle 110. In one embodiment, processor 122 is an embedded systemcontroller. In another embodiment, processor 122 controls communicationsbetween telematics unit 120, wireless carrier system 140, and callcenter 170. In another embodiment, processor 122 controls communicationsbetween the wireless access point node 134 and nodes of a mobile ad hocnetwork. In one embodiment, a speech-recognition application isinstalled in processor 122 to translate human voice input throughmicrophone 130 into digital signals. Processor 122 generates and acceptsdigital signals transmitted between telematics unit 120 and a vehiclecommunication bus 112 that is connected to various electronic modules inthe vehicle 110. In one embodiment, the digital signals activate aprogramming mode and operation modes, as well as provide for datatransfers. In another embodiment, a vehicle data upload (VDU) utilityprogram facilitates the transfer of instructions and data requests tovehicle 110 and captured test fleet data.

Vehicle communication bus 112 sends signals to various units ofequipment and systems within test vehicle 110 to perform variousfunctions such as monitoring the operational state of vehicle systems,collecting and storing data from the vehicle systems, providinginstructions, data and programs to various vehicle systems and callingfrom telematics unit 120. In facilitating interactions among the variouscommunication and electronic modules, vehicle communication bus 112utilizes bus interfaces such as controller-area network (CAN), J1850,International Organization for Standardization (ISO) Standard 9141, ISOStandard 11898 for high-speed applications, and ISO Standard 11519 forlower speed applications. Additionally, captured test vehicle 110, inone embodiment, sends and receives signals from a discrete I/O device111 using discrete wiring.

Test vehicle 110, via telematics unit 120, sends and receives radiotransmissions from wireless carrier system 140. Wireless carrier system140 is implemented as any suitable system for transmitting a signal frommobile vehicle 110 to communication network 142. Wireless carrier system140 incorporates any type of telecommunications in which electromagneticwaves carry signal over part of or the entire communication path. In oneembodiment, wireless carrier system 140 transmits analog audio, digitalaudio (including, but not limited to, CDMA, TDMA, FDMA, GSM) and/orvideo signals. In an example, wireless carrier system 140 transmitsanalog audio and/or video signals such as those sent from AM and FMradio stations and transmitters, or digital audio signals in the S band(approved for use in the U.S.) and L band (used in Europe and Canada).In one embodiment, wireless carrier system 140 is a satellite broadcastsystem broadcasting over a spectrum in the “S” band (2.3 GHz) that hasbeen allocated by the U.S. Federal Communications Commission (FCC) fornationwide broadcasting of satellite-based Digital Audio Radio Service(DARS).

Communication network 142 includes services from one or more mobiletelephone switching offices and wireless networks. Communication network142 connects wireless carrier system 140 to land network 144.Communication network 142 is implemented as any suitable system orcollection of systems for connecting wireless carrier system 140 tomobile vehicle 110 and land network 144. In one example, wirelesscarrier system 140 includes a short message service, modeled afterestablished protocols such as IS-637 SMS standards, IS-136 air interfacestandards for SMS, and GSM 03.40 and 09.02 standards. Similar to paging,an SMS communication could be broadcast to a number of regionalrecipients. In another example, the carrier system 140 uses services inaccordance with other standards, such as, for example, IEEE 802.11compliant wireless systems and Bluetooth compliant wireless systems.

Land network 144 is a public-switched telephone network (PSTN). In oneembodiment, land network 144 is implemented as an Internet protocol (IP)network. In other embodiments, land network 144 is implemented as awired network, an optical network, a fiber network, another wirelessnetwork, or any combination thereof. Land network 144 is connected toone or more landline telephones. Land network 144 connects communicationnetwork 142 to user computer 150, web-hosting portal 160, and callcenter 170. Communication network 142 and land network 144 connectswireless carrier system 140 to web-hosting portal 160 and call center170.

Client, personal or user computer 150 includes a computer usable mediumto execute Internet browser and Internet-access computer programs forsending and receiving data over land network 144 and optionally, wiredor wireless communication networks 142 to web-hosting portal 160 andtest vehicle 110. Personal or user computer 150 sends captured testfleet data requests to web-hosting portal through a web-page interfaceusing communication standards such as hypertext transport protocol(HTTP), and transport-control protocol Internet protocol (TCP/IP). Inone embodiment, the data includes directives to change certainprogramming and operational modes of electronic and mechanical systemswithin test vehicle 110. In another embodiment, the data includesdirectives to send certain data such as operational modes of electronicand mechanical systems within test vehicle 110. In operation, a user,such as, for example, a vehicle designer or manufacturing engineer,utilizes user computer 150 to access real-time test fleet data from testvehicle 110 that is cached or stored in web-hosting portal 160. Capturedtest fleet data from client-side software is transmitted to server-sidesoftware of web-hosting portal 160. In one embodiment, captured testfleet data is stored at web-hosting portal 160. In another embodiment,client computer 150 includes a database (not shown) for storing receivedcaptured fleet data. In yet another embodiment, a private Local AreaNetwork (LAN) is implemented for client computer 150 and Web hostingportal 160, such that web hosting portal is operated as a VirtualPrivate Network (VPN).

Web-hosting portal 160 includes one or more data modems 162, one or moreweb servers 164, one or more databases 166, and a network 168. In oneembodiment, web-hosting portal 160 is connected directly by wire to callcenter 170, or connected by phone lines to land network 144, which isconnected to call center 170. In another embodiment, web-hosting portal160 is connected to call center 170 without a direct wire connection,but with a connection allowing communication between the call center 170and the web-hosting portal 160. Web-hosting portal 160 is connected toland network 144 by one or more data modems 162. Land network 144 sendsdigital data to and from modem 162; data that is subsequentlytransferred to web server 164. In one implementation, modem 162 residesinside web server 164. Land network 144 transmits data communicationsbetween web-hosting portal 160 and call center 170.

Web server 164 receives various data requests or instructions from usercomputer 150 via land network 144. In alternative embodiments, usercomputer 150 includes a wireless modem to send data to web-hostingportal 160 through a wireless communication network 142 and a landnetwork 144. Data is received by modem 162 and sent to one or more webservers 164. In one embodiment, web server 164 is implemented as anysuitable hardware and software capable of providing web services totransmit and receive data from user computer 150 to telematics unit 120in test vehicle 110. Web server 164 sends to or receives datatransmissions from one or more databases 166 via network 168. Web server164 includes computer applications and files for managing captured testfleet data.

In one embodiment, one or more web servers 164 are networked via network168 to distribute captured test fleet data among its network componentssuch as database 166. In an example, database 166 is a part of or aseparate computer from web server 164. In one embodiment, web-server 164sends data transmissions with captured test fleet data to call center170 via modem 162, and through land network 144.

Call center 170 is a location where many calls are received and servicedat the same time, or where many calls are sent at the same time. In oneembodiment, the call center is a telematics call center, facilitatingcommunications to and from telematics unit 120 in test vehicle 110. Inan example, the call center is a voice call center, providing verbalcommunications between an advisor in the call center and a subscriber ina mobile vehicle. In another example, the call center contains each ofthese functions. In other embodiments, call center 170 and web-hostingportal 160 are located in the same or different facilities.

Call center 170 contains one or more voice and data switches 172, one ormore communication services managers 174, one or more communicationservices databases 176, one or more communication services advisors 178,and one or more bus systems 180.

Switch 172 of call center 170 connects to land network 144. Switch 172transmits voice or data transmissions from call center 170, and receivesvoice or data transmissions from telematics unit 120 in mobile vehicle110 through wireless carrier system 140 and/or wireless access pointnode 136, communication network 142, and land network 144. Switch 172receives data transmissions from, and sends data transmissions to, oneor more web-hosting portals 160. Switch 172 receives data transmissionsfrom, or sends data transmissions to, one or more communication servicesmanagers 174 via one or more bus systems 180.

Communication services manager 174 is any suitable hardware and softwarecapable of providing communication services to telematics unit 120 inmobile vehicle 110. Communication services manager 174 sends to orreceives data transmissions from one or more communication servicesdatabases 176 via bus system 180. Communication services manager 174sends to or receives data transmissions from one or more communicationservices advisors 178 via bus system 180. Communication servicesdatabase 176 sends to or receives data transmissions from communicationservices advisor 178 via bus system 180. Communication services advisor178 receives from or sends to switch 172 voice or data transmissions.

Communication services manager 174 facilitates one or more services,such as, but not limited to, enrollment services, navigation assistance,directory assistance, roadside assistance, business or residentialassistance, information services assistance, emergency assistance, andcommunications assistance and vehicle data management services.Communication services manager 174 receives service requests forcaptured test fleet data from a user via user computer 150, web-hostingportal 160, and land network 144. Communication services manager 174transmits and receives operational status, instructions and other typesof vehicle data to telematics unit 120 in test vehicle 110 throughwireless carrier system 140, communication network 142, land network144, wireless access point node 136 voice and data switch 172, and bussystem 180. Communication services manager 174 stores or retrievesvehicle data and information from communication services database 176.Communication services manager 174 provides requested information tocommunication services advisor 178.

In one embodiment, communication services advisor 178 is a real advisor.In another embodiment, communication services advisor 178 is implementedas a virtual advisor. In an example, a real advisor is a human being atservice provider service center in verbal communication with servicesubscriber in mobile vehicle 110 via telematics unit 120. In anotherexample, a virtual advisor is implemented as a synthesized voiceinterface responding to requests from telematics unit 120 in mobilevehicle 110.

Communication services advisor 178 provides services to telematics unit120 in mobile vehicle 110. Services provided by communication servicesadvisor 178 include enrollment services, navigation assistance,real-time traffic advisories, directory assistance, roadside assistance,business or residential assistance, information services assistance,emergency assistance, and communications assistance. Communicationservices advisor 178 communicates with telematics unit 120 in mobilevehicle 110 through wireless carrier system 140, communication network142, and land network 144 using voice transmissions, or throughcommunication services manager 174 and switch 172 using datatransmissions. Switch 172 selects between voice transmissions and datatransmissions.

Test vehicle 110 initiates service requests to call center 170 bysending a voice or digital-signal command to telematics unit 120 whichin turn, sends an instructional signal or a voice call through wirelessmodem 124, wireless carrier system 140, communication network 142, andland network 144 to call center 170. In another embodiment, the servicerequest is for a vehicle data upload (VDU) that initiates a datatransfer between test vehicle 110 and service center 170 or web hostingportal 160. In another embodiment, the mobile vehicle 110 receives arequest from call center 170 to send various vehicle data from mobilevehicle 110 through telematics unit 120 through wireless modem 124,wireless access point node 136, wireless carrier system 140,communication network 142, and land network 144 to call center 170. Inone embodiment, one or more triggers stored in the telematics unit 120cause the test vehicle to initiate a service request. A trigger is anevent with associated data that interacts with a set of parameterretrieval definitions. A trigger is, for example, a number of ignitioncycles, a specific time and date, an expired time, a number ofkilometers, a request for continuous operation and the like.

A vehicle configuration is a collection of vehicles, triggers, parameterretrieval definitions, and parameters. Triggers cause parameterretrieval definitions to be examined and executed. Parameter retrievaldefinitions identify specific parameters to be collected on a vehicleand communicated to a remote facility, such as a call center, where theparameters are parsed and analyzed. Parameter retrieval definitions aredependent on module hardware and software revisions resident withinvehicles. Parameters contain the specific data requested by theparameter retrieval definitions. The parameter retrieval definitionscontain the criteria to retrieve specific data embodied withinparameters.

Parameter retrieval definitions are examined in response to activationof a trigger. For example, the parameter retrieval definitions arecontained in a table or an array and are sequentially index through byan application program. Parameter retrieval definitions may contain, forexample, criteria for retrieving oil life information or odometerinformation.

Triggers are initially programmed into or downloaded into telematicsunit 120. An application program resident in telematics unit 120examines the conditions specified to generate an event specified by thetrigger. For example, if the trigger resident in the telematics unitspecifies a request for an event at 2800 miles, then the odometer orother mileage measuring device in the vehicle is examined on a polled orevent driven basis and when the mileage measuring device indicates amileage of 2800 miles, an event is generated. This event is typically,for example, a phone call generated by the telematics unit into atelematics call center.

Once the event manifested as a phone call into the telematics callcenter is established at the call center, the parameter retrievaldefinitions for that vehicle that initiated the call are examined. Eachparameter retrieval definition is subsequently formatted andcommunicated to the calling vehicle. The calling vehicle examines andacts on the received parameter retrieval definitions. For example, aparameter retrieval definition may define a request for oil lifeinformation. Oil life information is subsequently collected, formatted,and communicated to the call center. As another example, a parameterretrieval definition requests an odometer reading. Odometer informationis collected, formatted, and communicated to the call center. The datais collected in a database at the call center and is maintained andanalyzed at the call center, wherein the data is transient at thetelematics unit. In one embodiment, the data may be maintained andanalyzed at the telematics unit.

FIG. 2 is a block diagram of an illustrative operating environment forinteractive vehicle design in accordance with an embodiment of thepresent invention. FIG. 2 shows captured test fleet system 200 includinga test fleet vehicle 210 having at least one vehicle system module 220and a vehicle telematics unit 230. A service center 270 is shown incommunication with the captured test fleet vehicle 210. The servicecenter is shown including a database 276. The vehicle system module 220is shown including executable command programs to monitor 221 and storedata 222 of a vehicle system. The vehicle telematics unit 230 is shownincluding executable command programs to monitor 231 and store data 232of a vehicle system, and executable programs and triggers 233 forinitiating communication with the service center 270. The service center270 is shown in communication with clients for quality assurance 240,design 250 and production 260.

Test vehicle 210 is any vehicle, such as, for example a pilot vehicle,that is operated within a captured test fleet of vehicles enabled fortest fleet data communication through a telematics service provider. Thecaptured test fleet includes a plurality of test vehicles of similar anddifferent vehicle models that are enabled to communicate with a servicecenter to allow real-time and cached field monitoring of vehicle designand operational parameters in the test vehicles. In one embodiment, acaptured test fleet includes approximately fifteen to twenty thousandselected vehicles. In another embodiment, the captured test fleetcomprises less than 50 selected test vehicles. The captured test fleetsystem 200 is configurable for operation with any number of testvehicles depending on the data desired and the purpose of the datacollection, such as for development, design and manufacturing exercises.

Telematics unit 230 is, for example, telematics unit 120 discussed withreference to FIG. 1, or any telematics unit configured to allow theservices described in this example.

Vehicle system module 220 is any device, such as, but not limited to, apower train control module (PCM) that is designed to monitor a system ofvehicle 210. The vehicle control module is enabled to receive datacommunications and instructions from other devices, such as for example,telematics unit 230 through a vehicle communications bus. In an example,other types of vehicle system modules include modules for brake andsteering control, modules for monitoring catalytic conversion,suspension control modules and the like. In an embodiment, vehiclecontrol modules detect and/or generate diagnostic trouble codes (DTC).

Service center 270 is, for example, a service provider center such asdescribed with reference to call center 170 of FIG. 1, or a serviceprovider center configured to provide the services described in thisexample. In one embodiment, service center 270 is implemented as aweb-server as described with reference to web-server 160 of FIG. 1.

Database 276 is any database for storing captured test fleet data. Inone embodiment, database 276 is a relational database having unique dataentries for each test vehicle operated within a captured test fleet.Each unique vehicle entry of the database 276 is associated with a testfleet identifier that identifies the vehicle and defines the vehicle asa captured test fleet member. In one embodiment, a test fleet identifieris a vehicle identification number (VIN). In another embodiment, a testfleet identifier is an electronic serial number (ESN) of a telematicsdevice, a system identification (SID) number of a telematics device, ormobile identification number (MIN) assigned to a telematics device. Inone embodiment, the database 276 includes relational associations toprovide correlated captured test fleet data for statistical analysis,such as similar vehicle system information from a plurality of testvehicles 210.

A client is any entity or computing device that interacts with capturedtest vehicle data, such as a vehicle design center, an engineering teamor a manufacturing production group where a client 150 such as describedwith reference to FIG. 1 is used to facilitate receiving and process thecaptured test fleet data. In one embodiment, the client is a computer orserver system that manages captured test fleet data and providesanalysis to users. In another embodiment, the client is a user or groupof users that access captured test fleet data through a web-portal, aservice center 270 or another data communicating regime. Qualityassurance client 240 is any client that manages quality assurance for avehicle manufacturing process. Design client 250 is any client thatmanages vehicle design for a vehicle manufacturing process. Productionclient 260 is any client that manages vehicle production for a vehiclemanufacturing process.

In operation, the captured test fleet system operates a plurality oftelematics enabled test vehicles 210 that communicate test data to theservice center 270 in a virtual private network (VPN) to providereal-time and cached vehicle test data for vehicle prototyping, design,development and manufacture. A test fleet identifier stored in database276 and test vehicle 210 identifies a test vehicle as a member of a testfleet that has private communication privileges with service center 270and clients. Service center 270 provides captured test fleet datawarehousing and caching for various test data collected from testvehicle 210 and vehicle system module 220 while operating under fieldtest conditions. In one embodiment, service center 270 is enabled torequest data from test vehicle 210, or to relay a data request from aclient to one or more test vehicles 210. In another embodiment, testvehicle 210 is enabled to provide periodic or continuous data transfersto service center 270 or to a client through serviced center 270. Aninteractive wireless real-time vehicle design and manufacturing processis enabled through the use of captured test fleet system 200 when a testvehicle 210 is directed to monitor specific vehicle and vehicle systemparameters by a service center or client.

FIG. 3 is block diagram of a captured test fleet database in accordancewith an embodiment of the present invention. In one embodiment, database376 is a relational database having captured test fleet data recordsassociated with test vehicle operated in a captured test fleet.

Database 376 includes one or more captured test vehicle data entriescorresponding to test vehicles operated in a captured test fleet systemas described with reference to FIG. 2. In the embodiment shown in FIG.3, a captured test fleet database entry 300 includes test vehicle datacomponents such as a release number records 310, sequential data requestrecords 320, 340, 360 and configuration data records 330, 350 and 370.Each test data component is available as an individual record that maybe manipulated for statistical or other analysis. In one embodiment,data request records identify sequential data requests, such as, forexample record number N and the next sequential record number N+1, sentto a specific test vehicle associated with a test fleet identifier. Inanother embodiment, data request records identify specific data requestssent to a plurality of test vehicles associated with a test fleetidentifier. In an embodiment, configuration data records identifysequential configuration data, such as, for example record number N andthe next sequential record number N+1, received from a specific testvehicle associated with a test fleet identifier. In still anotherembodiment, configuration data records identify vehicle test datacollected from a plurality of test vehicles of a captured test fleet. Inan example, a configuration data record describes the monitoringconfiguration of one or more vehicle systems in a specific test vehicleof the captured test fleet. In another embodiment, additional datarecords (not shown) are stored in database 376 that are associated withcaptured test fleet vehicles. In an embodiment, database 376 containsany type of captured test fleet data obtained from a test fleet vehiclethat is usable by a client for vehicle design, manufacture and qualityassurance.

FIG. 4 is a process flow diagram of a method for interactive design andmanufacture of a vehicle in accordance with an embodiment of the presentinvention. In an embodiment, a captured test fleet vehicle communicationsystem 100 is employed with certain steps of process 400. Process 400begins in step 401.

In step 401, a vehicle is designed. An initial vehicle design forms thebasis for the interactive design and manufacturing process 400.Designing an initial vehicle commences the design and manufactureprocess 400. Conventional vehicle design techniques are well known inthe art and therefore will not be further discussed.

In step 402, a test vehicle is built. The test vehicle is built at anytime after a vehicle is designed or an initial design is improved. Oneor more test vehicles are built in step 402. In one example, the testvehicles are production intent prototypes.

In step 403, a captured test fleet is operated. The captured test fleetis operated at any time after a test vehicle is built and enabled forcommunication with a service provider in a captured test fleet.Operating a captured test fleet includes monitoring and collecting datafrom test fleet vehicles systems, storing the collected data, providingthe data to a production design team for analysis and iterative designrefinement, and then altering initial vehicle design based on theanalysis and design refinement. Various collected vehicle system data iscommunicated from a test vehicle having a telematics unit 120 through aservice provider in a virtual private network comprised of one or moretest vehicles, a service provider and a design center client. In oneembodiment, requests for vehicle data are sent from a client, and avehicle responds to the data request by sending the requested data tothe client through a service provider. In another embodiment, a testvehicle is configured to automatically provide vehicle system data to aservice center based on trigger events, such as, for example, a specifictime, an expired amount of time, a number of ignition cycles and thelike.

In step 404, a vehicle is produced. Producing a vehicle includes smalland large scale manufacturing of a designed production vehicle.

In step 405, a production fleet is operated. The production test fleetis operated at any time after a production vehicle is produced andenabled for communication with a service provider. The production fleetis operated between the manufacture and sale of a production vehicle,such as, for example, during a launch period, or a dealership testdriving program.

In step 406, vehicles are sold to consumers. The vehicle is sold to aconsumer at any time after vehicle production and delivery to a salelocation, such as an auto dealership, for example.

In step 407, a customer operates a purchased vehicle. A vehicle isoperated by a consumer at any time after the vehicle is purchased.

In step 408, production vehicles are monitored. In one embodiment,production vehicles are monitored at any time after a consumer beginsoperating a production vehicle. The monitoring comprises monitoring andcollecting data from production vehicle systems, storing the collecteddata, providing the data to a production design team for analysis anditerative design refinement. Various collected production vehicle systemdata is communicated from a production vehicle having a telematics unit120, 230 through a service provider in a virtual private networkcomprised of one or more production vehicles, a service provider and adesign or quality assurance client. In one embodiment, requests forvehicle data are sent from a client, and a vehicle responds to the datarequest by sending the requested data to the client through a serviceprovider. In another embodiment, a test vehicle is configured toautomatically provide vehicle system data to a service center based ontrigger events, such as, for example, a specific time, an expired amountof time, a number of ignition cycles and the like. In anotherembodiment, step 408 is performed on test vehicles.

In step 409, improvements are identified. Improvements in productionvehicle design are identified through analysis of production vehiclesystem data collected in the step of monitoring 408.

In step 410, vehicle improvements are designed based on the identifiedimprovements. The vehicle improvements are designed at any time afterthe collected vehicle data is analyzed and design improvements areidentified. The improved design is then provided to vehiclemanufacturing facilities, a dealership or vehicle service center and thelike.

In step 411, vehicles are improved post sale. A vehicle is improved atanytime after a production vehicle design is improved. In oneembodiment, a vehicle is improved after sale through an upgrade serviceat an auto dealership. In an example, a production vehicle is improvedat an auto dealership by downloading improved software and/or installingnew hardware.

In other embodiments of the invention, additional methods for vehicledesign and manufacture are described. In one embodiment, a method ofvehicle manufacture comprises designing a vehicle, building at least onepilot vehicle of the designed vehicle, installing a telematics units120, 130 in each of the pilot vehicles, configuring the telematics unit120, 230 to monitor systems of the pilot vehicle during vehicleoperation, operating the pilot vehicle in a captured test fleet,obtaining data from the telematics unit 120, 230 during the operating ina captured test fleet, altering vehicle design data in response to theobtained data and, building a production vehicle with the designinfluenced by the altered vehicle design data.

In one embodiment, the captured test fleet comprises at least one pilotvehicle having a unique identification and wherein each at least onevehicle has an associated captured test fleet identifier stored in arelational database.

In another embodiment, obtaining data from the telematics unit 120, 230includes receiving a request for captured test fleet data, determiningvehicles having captured test fleet identifiers corresponding to therequest, sending a data retrieval request to vehicles based on thedetermination, and receiving data from the vehicles responsive to thedata retrieval request.

In still another embodiment, altering vehicle design data in response tothe obtained data includes providing the obtained data to a vehicledesign center, analyzing the obtained data at the vehicle design center,identifying a modification to the designed vehicle to improve thedesigned vehicle based on the obtained data, and providing new vehicledesign data based on the identified modification. In another embodiment,new vehicle design data comprises improved vehicle component designdata.

Another method of vehicle manufacture describes designing at least onevehicle, building at least one pilot vehicle of the at least onedesigned vehicle, installing telematics units 120, 230 in the at leastone pilot vehicle, operating the at least one pilot vehicle in a testfleet; for each pilot vehicle of the test fleet, monitoring performanceof at least one vehicle system within the pilot vehicle, first storingdata within a controller in the pilot vehicle in response to themonitoring, automatically triggering within the telematics unit 120, 230a telematics connection from the pilot vehicle to a service centerwherein the telematics connection is triggered independent of a locationof the pilot vehicle, communicating the first stored data to the servicecenter; second storing the first stored data in the service center,providing the second stored data to at least one person capable ofinfluencing design of the at least one vehicle and the at least onevehicle system and modifying at least one vehicle system or component ofthe designed vehicle in response to the second stored data.

In an embodiment, automatically triggering within the telematics unit120, 230 a telematics connection from the pilot vehicle to a servicecenter includes determining an upload trigger occurrence.

In another embodiment, the upload trigger is selected from the groupconsisting of a count of ignition cycles, expired days, kilometersrecorded, a specific time, a continuous upload request and a userinitiated call request.

In yet another embodiment, storing the first stored data in the servicecenter includes associating the first stored data with an entry in arelational database based on a test fleet identifier, the databasehaving a unique entry corresponding to each at least one pilot vehicleof the test fleet, and storing the first stored data to the unique entrycorresponding to the pilot vehicle that communicated the data to theservice center.

FIG. 5 is a process flow diagram of a method for providing captured testfleet data from a test vehicle in accordance with an embodiment of thepresent invention. In an embodiment, a captured test fleet vehiclecommunication system 100 is used to implement the method of process 500.Process 500 begins in step 501.

In step 501 a call is triggered from a vehicle. The call is triggeredbased on a detected condition such as a specified number of ignitioncycles, expired number of days, kilometers recorded, a specific time, acontinuous upload request and a user initiated call request, that isprogrammed into a telematics device in a vehicle. The call is triggeredany time a triggering condition is detected at the vehicle. In anotherembodiment, a user initiates a call via an utterance or button press.

In step 502, a test service center receives the call and a connection isestablished with a vehicle. A service provider relays a wireless carriercommunication request from the vehicle to the service center. Theservice center answers the request and establishes a connection. Theconnection is enabled at any time after the call center receives therequest, and before termination of the connection.

In step 503, vehicle information and scheduled requests are looked up ina database. A database, such as database 376 of FIG. 3 for example,contains database entries 300 having records of vehicle data such asinformation and scheduled requests. The database entries are accessed atany time after the call is connected.

In step 504, an upload is requested from a vehicle. A vehicle dataupload (VDU) directs data to be either transferred from a vehicle to aservice center or, as in the present embodiment, from a service centerto a vehicle through the connected call or another communicationchannel. The VDU request occurs at any time after the call from thevehicle is connected to the call center.

In step 505, the data upload is completed. The vehicle data uploadtransfers data requests, instructions and other data to the vehicle fromthe service center.

In step 506, the data upload is stored. Memory 128 in the vehicle storesthe data transferred to the vehicle in the VDU.

In step 507, scheduled bus requests are performed. In one embodiment,contents of the vehicle data upload stored to memory include vehicle busrequests that specify systems and modules of the vehicle that areaccessed via a vehicle communication bus 112. A bus request is any datarequest that is communicated to a system or module of a vehicle over avehicle communication bus 112. In an embodiment, a schedule of datarequests is included in a vehicle data upload such that data requestsare distributed to vehicle systems based on the schedule.

In step 508, request responses are stored. In response to the datarequest, a vehicle system module provides system monitoring data suchas, for example, operating parameters, diagnostic trouble codes, andfailure logs or codes.

In step 509, vehicle data upload functions are configured. In anembodiment, a vehicle data upload includes configuration parameters forthe VDU function in the vehicle. The VDU functions are updated atanytime after the configuration data is received. In one embodiment, theVDU is configured after each VDU event.

In step 510, the service center communication is terminated. In oneembodiment, the vehicle telematics unit 120, 230 disconnects the call.In another embodiment, the service center terminates the connection.

In step 511, a database is marked with a task complete and a next taskis indexed. One or more records of a database entry 300 for the vehicleare updated to reflect that scheduled bus requests and other data andservices were communicated to the vehicle. A counter is indexed and thenext database vehicle entry is accessed. The process then returns tostep 502 and commences for a new vehicle having a test fleet identifierassociated with the database entry.

In one embodiment, process 500 continues until each vehicle record inthe database is updated. In another embodiment, process 500 continuesuntil terminated by another process or by a user request.

FIG. 6 is a process flow diagram of a method for managing captured testfleet data in accordance with an embodiment of the present invention. Inan embodiment, a captured test fleet vehicle communication system 100 isemployed to implement process 600. Process 600 begins in step 601.

In step 601, a vehicle information database is generated. In anembodiment, the information database comprises a relational database ofvehicle entries corresponding to vehicles of a captured test fleet. Eachvehicle entry is associated with a vehicle having a captured fleetidentifier, and contains one or more records of vehicle data such asinformation and scheduled requests. In an embodiment, the vehicledatabase is a captured test fleet database as described with referenceto FIGS. 1-3. In an embodiment, the vehicle database is generated inresponse to a request from a client that desires a specific type ofvehicle data to facilitate vehicle design, development, engineering ormanufacturing processes.

In step 602, remote vehicle communication is enabled. A vehicletelematics device is operated within a service provider network toenable remote vehicle communications.

In step 603, a vehicle is identified. The vehicle is identified with acaptured test fleet identifier such as, for example, a vehicleidentification number (VIN). In another embodiment, a test fleetidentifier is an electronic serial number (ESN) of a vehicle telematicsunit 120, 230, a station identification (STID) number of a telematicsunit 120, 230, or a mobile identification number (MIN) assigned to atelematics unit 120, 230.

In step 604, vehicle data in a database is accessed corresponding to theidentified vehicle. The vehicle data is accessed at any time after thevehicle is identified. In an embodiment, accessed data includes datarequests and vehicle data upload configuration data.

In step 605, data from the identified vehicle is requested. In anembodiment, a data request includes scheduled bus requests and systeminformation such as, for example, diagnostic trouble codes. In anotherembodiment, the data is requested through a vehicle data upload (VDU)operation. In another embodiment, the requested vehicle data is providedto a service provider in response to the data request.

In step 606, a vehicle monitor is configured. A telematics unit 120, 230in a vehicle receiving the data request or a vehicle data uploadconfigures one or more vehicle system monitors to collect the requesteddata. In an embodiment, collected vehicle system data is provided to aservice provider in response to the data collecting.

In step 607, the vehicle connection is terminated. In one embodiment,the vehicle telematics unit 120, 230 disconnects the call. In anotherembodiment, the service center terminates the connection.

In step 608, an entry for the identified vehicle is updated. In anembodiment, data received from the identified vehicle in response to thedata request is updated in a record. In another embodiment, a record ofan interaction with a test vehicle is recorded, such as for example, arecord of a VDU event to the vehicle.

In step 609, updated vehicle data is provided to engineering. Anengineering client is provided with data from vehicle entries andrecords of test fleet database for analysis and interactive designrefinement, vehicle development or manufacturing processes.

In step 610, the database is updated based on engineering input. In anembodiment, an engineering client provides updated vehicle entries afteranalysis of various vehicle data records. In one embodiment, the updatedentries describe new vehicle system monitoring configurations toimplement monitoring of specific vehicle systems and parameters.

In step 611, the next database entry is indexed. After the vehicle entryis updated, the database indexes to the next vehicle entry in thedatabase and process 600 returns to step 602 to update the data entryfor the new vehicle entry. In an embodiment, the indexing is sequential.In another embodiment, the indexing is based on the type of data thathas been provided by the engineering client. In an example, anengineering client wishes to perform a survey of all vehicle systems ofa particular model of vehicle in the captured test fleet. The index isthen associated with the database entries for each vehicle of theparticular vehicle model under review. In one embodiment, process 600continues until each vehicle record in the database is updated. Inanother embodiment, process 600 continues until terminated by anotherprocess or by a user or client request.

FIG. 7 is a process flow diagram of a method of obtaining captured testfleet data for vehicle design in accordance with an embodiment of thepresent invention. In an embodiment, a captured test fleet vehiclecommunication system 100 is employed to implement the method of process700. Process 700 begins in step 710.

In step 710, a database is provided including a list of vehiclesassociated with a captured test fleet. In an embodiment, the database isprovided by a client or a telematics service provider. In oneembodiment, the database is generated by a service provider servercomputer based on one or more test fleet identifiers that are associatedwith one or more captured test fleet vehicles.

In step 720, a request for captured test fleet data is received. Therequest for captured test data occurs any time after the database isprovided. In an embodiment, the request for captured test fleet data isreceived from a client. In another embodiment, the request for capturedtest fleet data is received from a vehicle design center.

In step 730, vehicles having test fleet identifiers corresponding to therequest are determined. In an embodiment, a test fleet identifier is avehicle identification number (VIN). In another embodiment, a test fleetidentifier is an electronic serial number (ESN) of a vehicle telematicsunit 120, 230, a system identification (SID) number of a telematics unit120, 230, or a mobile identification number (MIN) assigned to atelematics unit 120, 230. In yet another embodiment, the test fleetidentifier is vehicle model data. In an embodiment, determining vehicleshaving captured test fleet identifiers corresponding to the requestincludes searching the database and identifying each vehicle data entryfrom the vehicle list having a captured test fleet identifier associatedwith the requested captured test fleet data.

In step 740, a data retrieval request is sent to vehicles based on thevehicle determination. A captured test vehicle system 100 is implementedto provide communication between a vehicle and the database. A vehicletelematics device is operated within a service provider network toenable remote vehicle communications. In another embodiment, a dataretrieval request includes scheduled bus requests and system informationsuch as, for example, diagnostic trouble codes. In another embodiment,the data is requested from a vehicle through a vehicle data upload (VDU)operation. In another embodiment, the requested vehicle data is providedto a service provider in response to the data request.

In step 750, data is received from the vehicles responsive to the dataretrieval request. In an embodiment, the service provider systemprovides communication between a vehicle and the database. The data isreceived at any time after the data request is sent to the vehicle. Inone embodiment, the captured vehicle test system is configured toprovide a continuous data transfer between the vehicle and the database.In another embodiment, the captured vehicle test system is configured toprovide a discrete data transfer between the vehicle and the database atregular intervals.

An embodiment further includes associating the received data with anentry in the database based on the test fleet identifier of the vehiclecorresponding to the request and storing the received data to thedatabase entry.

Another embodiment further includes providing the data stored to thedatabase to a vehicle design center responsive to the request forcaptured test fleet data.

In an embodiment, the captured test fleet data is selected from thegroup consisting of diagnostic trouble codes, vehicle readiness flags,odometer readings, enrollment data, environmental data such astemperature and humidity, current vehicle location, vehicle systemoperating parameters and history codes. In one embodiment, process 700terminates after data is received in step 750. In another embodiment,process 700 returns to step 720 (not shown) and continues until anotherprocess or a user request terminates the process.

FIG. 8 is a process flow diagram of a method for real-time wirelessinteractive test vehicle data collection in accordance with anembodiment of the present invention. In an embodiment, a captured testfleet system 100 and a captured test fleet vehicle design operatingenvironment 200 are employed to implement process 800. Process 800begins in step 810.

In step 810, a test vehicle is operated in a captured test fleet. Thecaptured test fleet includes a plurality of test vehicles of similar anddifferent vehicle models that are enabled to communicate with a servicecenter to allow real-time and cached field monitoring of vehicle designand operational parameters in the test vehicles. The captured test fleetsystem is configurable for operation with any number of test vehiclesdepending on the data desired and the purpose of the data collection,such as for development, design and manufacturing exercises.

In step 820, the performance of a vehicle system within the test vehicleis monitored. A vehicle system module 220 such as, for example, apowertrain control module is configured to monitor various operatingparameters and conditions during vehicle operation. In one embodiment,the system monitoring occurs at any time that a controller is enabled toreceive data. In another embodiment, a schedule of communication busrequests is stored to a vehicle during a vehicle data upload (VDU). Theschedule controls when and what is monitored by the vehicle systemmodules 220.

In step 830, vehicle system performance data is stored within acontroller in the test vehicle. In an embodiment, a vehicle telematicsunit 120, 230 provides a controller or equivalent processor andcontroller functions to direct the storing of the performance data. Inan embodiment, to alleviate consumption of valuable vehicle systemmodule 220 memory resources, the telematics unit 120, 230 is configuredto periodically transfer any collected data from each vehicle systemmodule 220.

In step 840, a wireless telematics connection is established between thetest vehicle and a service center. In one embodiment, a service providerprovides the telematics connection. In one embodiment, a vehicletelematics unit 120, 230 establishes the telematics connection. Inanother embodiment, a service provider establishes the telematicsconnection. In an embodiment, triggers stored in the vehicle telematicsdevice invoke a wireless connection with a service provider.

In step 850, the stored performance data is communicated to the servicecenter. In one embodiment, all vehicle system module 220 data that isstored in the telematics device memory is transferred to a serviceprovider. The stored performance data are communicated at any time afterthe data is stored within a controller.

In step 860, the received performance data is stored to a database inthe service center. In one embodiment, all captured test fleet vehicledata received from test fleet vehicles is stored to a test vehiclerelational database. The database contains entries for each capturedtest vehicle of the fleet. Each vehicle entry is associated with aspecific test vehicle having a captured fleet identifier, and containsone or more records of test vehicle data such as information andscheduled requests. In an embodiment, the vehicle database is a capturedtest fleet database as described with reference to FIGS. 1-3. In anotherembodiment, the vehicle database is generated in response to a requestfrom a client that desires a specific type of vehicle data to facilitatevehicle design, development, engineering or manufacturing processes.

An embodiment further includes requesting performance data for a vehiclesystem from a test vehicle wherein the request is initiated from theservice center.

Another embodiment further includes determining a trigger in thetelematics device wherein the wireless telematics device establishes awireless telematics connection between the test vehicle and a servicecenter to communicate the performance data to the service centerresponsive to the trigger determination.

Yet another embodiment further includes requesting performance data fora vehicle system from a test vehicle where the request is initiated froma vehicle design center via the service center.

Still another embodiment further includes providing the performance datastored to the database to a vehicle design center. And yet anotherembodiment further includes analyzing the obtained data at the vehicledesign center, identifying a modification to the designed vehicle toimprove the designed vehicle based on the obtained data and providingnew vehicle design data based on the identified modification.

Use of a mobile telephone network allows data to be uploaded to the callcenter from the telematics unit at any desirable time and from any placewhere the vehicle is located. In the event that the vehicle is not inoperation when the call center desires to upload data, the telematicsunit is programmed to upload data upon operation. Thus, in oneembodiment, the telematics unit is programmed to call the call centerupon beginning operation if the data upload request arrives while thevehicle is not in operation.

FIG. 9 is a block diagram of an illustrative operating environment for aweb-enabled configurable quality data collection tool in accordance withan embodiment of the present invention. In an embodiment, a capturedtest fleet vehicle communication system 100 is employed to implement theweb-enabled operating environment 900.

Web-enabled operating environment 900 includes a test vehicle 910,having test vehicle data collection components 920, and test vehiclecommunication components 930 which facilitate communication with one ormore databases 936. Database 936 is in communication with vehicle dataaccess web service 940, which communicates with a client 960 via a webportal framework 950.

Test vehicle 910 is any vehicle, such as for example, a pilot, test, orproduction vehicle that is operated within a captured test fleet ofvehicles enabled for test fleet data communication through a telematicsservice provider. Test vehicle 910 is, for example, test vehicle 210discussed with reference to FIG. 2, or any test vehicle configurable fordata collection as described in this example. The web-enabled operatingenvironment 900 is configurable for operation with any number of testvehicles based on the data desired and the purpose of data collection.

Vehicle data collection component 920 is any component of test vehicle910 that is configured to monitor a system or part of test vehicle 910.Vehicle data collection component 920 receives data communications andinstructions from other devices, such as vehicle communication component930. Vehicle data collection component monitors and collects data fromtest vehicle 910. Vehicle data collection component 920 includes, forexample vehicle system module 220 as discussed with reference to FIG. 2,or any component that collects data information about test vehicle 910.

Vehicle data collection component 920 sends and receives communicationsand instructions through the vehicle communication component 930.Vehicle communication component 930 is any component that facilitatescommunication between the test vehicle 910 and a remote node. In oneembodiment, vehicle communication component 930 includes a telematicsunit 230 as discussed with reference to FIG. 2.

The test vehicle 910 is in communication with database 936 via vehicledata communication component 930. Database 936 is any database forstoring test vehicle fleet data. Database 936 includes one or morecaptured test vehicle data entries corresponding to test vehiclesoperated in a captured test vehicle system. In one embodiment, database936 is a relational database having unique data entries for each testvehicle operated within a captured test fleet. Each test vehicle isassociated with a vehicle identifier in the database, which defines andassociates the test vehicle as part of a captured test fleet. In oneembodiment, a test vehicle identifier is a vehicle identification number(VIN). In another embodiment, a vehicle identifier is an electronicserial number (ESN) of a telematics device, a system identificationnumber (SID) of a telematics device, or mobile identification number(MIN) assigned to a telematics device. In another embodiment, vehicleidentifier is any characteristic that describes test vehicle attributessuch as make, model, odometer mileage, module identification, or thelike. Database 936 is, for example, database 276 as discussed withreference to FIG. 2, or any other database configured to store testvehicle data and provide the services described in this example. In oneembodiment, database 936 receives test vehicle data and sends data totest vehicle 910 via vehicle communication component 930.

Database 936 is in communication with a web portal framework 950 via avehicle data access web service 940. Vehicle data access web service 940facilitates the communication and transmission of test vehicle data fromdatabase 936 to the Internet. In one embodiment, vehicle data access webservice 940 is a web portal such as web-hosting portal 160 as discussedwith reference to FIG. 1. Database 936 is in direct communication withthe web portal framework 950. In another embodiment, vehicle data accessweb service 940 is a call center, such as for example call center 170,which receives and sends information to database 936. In an embodiment,the call center receives and filters data from database 936 and forwardsthe filtered data to the web portal framework 950.

Web portal framework 950 includes one or more vehicle data portlets 952and a vehicle data collection configuration portlet 954. Web portalframework 950 provides test vehicle data and parameters to a client 960and allows client 960 to request data from test vehicle 910. Web portalframework 950 is in direct communication with the Internet and vehicledata access web service 940. One or more vehicle data portlets 952receive test vehicle data from database 936 via vehicle data access webservice 940. Vehicle data portlet 952 provides vehicle data to a client960 via the structure of web portal framework 950. Vehicle datacollection configuration portlet 954 receives data from one or morevehicle data portlets 952 and receives requests from a client 960 toacquire further or different data from test vehicle 910. Client 960interacts with vehicle data collection configuration portlet 954 via webportal framework 950.

A client 960 is any entity or computing device that interacts with webportal framework 950 such as a vehicle design center, an engineeringteam, a production group, or a single user. In one embodiment, theclient is a user or group of users that access test vehicle data throughweb portal framework, such as, for example, quality assurance client240, design client 250, or production client 260 as discussed withreference to FIG. 1.

Client 960 executes Internet browser and Internet-access computerprograms for sending and receiving data over the Internet to access webportal framework 950. In one embodiment, the client 960 accesses webportal framework 950 to change vehicle data collection parameters viavehicle data collection configuration portlet 954 or to view collectedtest vehicle data via vehicle data portlet 952. In one embodiment, thedata sent by client 960 through vehicle data collection configurationportlet 952 includes directives to change certain programming andoperational modes of electronic and mechanical systems within testvehicle 910. In another embodiment, the data includes directives to sendcertain data such as operational modes of electronic and mechanicalsystems within test vehicle 910.

FIG. 10 is a process flow diagram of a method for remote configurationof test vehicle data capture in accordance with an embodiment of thepresent invention. In an embodiment, a captured test fleet system 100and a captured test fleet vehicle design operating environment 200 areemployed to implement process 1000. Process 1000 involves a testvehicle, which is configured to automatically provide vehicle systemdata to a service center based on specific trigger events. The processbegins at step 1005.

At step 1010, a client accesses an interface at a remote station. Aclient is any entity or computing device that interacts with capturedtest vehicle data, such as a vehicle design center, an engineering team,a manufacturing production group, or a single user where a client 150such as described with reference to FIG. 1 is used to facilitatereceiving and processing the captured test fleet data. In an embodiment,the interface is a web-portal, a service center 270, or another datacommunication regime. The client accesses the interface and sends arequest for a vehicle database.

At step 1020 a vehicle information database is provided to the client atthe interface. In an embodiment, the vehicle information databasecomprises a database of vehicle entries corresponding to vehicles of acaptured test fleet such as described with reference to FIG. 3. Eachvehicle entry in the database is associated with a vehicle capturedfleet identifier. In one embodiment, a test fleet identifier is avehicle identification number (VIN). In another embodiment, a test fleetidentifier is an electronic serial number (ESN) of a telematics device,a system identification (SID) number of a telematics device, or mobileidentification number (MIN) assigned to a telematics device. In anembodiment, the vehicle information database includes relationalassociations to provide correlated captured test fleet data forstatistical analysis, such as similar vehicle system information. Inanother embodiment, vehicles are identified and grouped together bymake, model, year, similar odometer mileage, oil life, or other relevantcharacteristics. In an embodiment, these characteristics act as testvehicle identifiers.

The database stores triggers for data collection for each test vehicle.In one embodiment, triggers are threshold conditions or events at theoccurrence of which data about an associated test vehicle is collectedat the test vehicle. In one embodiment, a client can create new triggerconditions to be stored in the database. In one embodiment, a client hasthe ability to create and eliminate triggers and parameter retrievaldefinitions. In an embodiment, the types of triggers are standardized tobe the same for all vehicles in a captured test fleet. In anotherembodiment, triggers are created separately for each different vehicleor group of vehicles in a captured test fleet.

At step 1030 the client selects one or more vehicles in the capturedtest fleet from the generated database. The client selects the vehiclesbased on their vehicle identifiers. In an embodiment, the client selectsthe test vehicle to configure data collection on the vehicle. Thevehicle can be selected based on any of its associated vehicleidentifier information such as its VIN, ESN, MIN, SIN, make, model,odometer reading, or other relevant characteristics. In anotherembodiment, the client selects a vehicle based on past occurrences ofspecific trigger events. In another embodiment, the client selects avehicle for troubleshooting based on a diagnostic trouble code (DTC)occurrence. In yet another embodiment, the client selects a group ofvehicles having similar vehicle identifier information. For example, theclient selects a group of associated vehicles having the same make andmodel.

At step 1040 the client configures the vehicle for data collection andassociates trigger conditions with the selected vehicle. In anembodiment, the client associates one or more trigger conditions withthe selected vehicle or group of vehicles. The selected triggercondition is associated with each test vehicle having the selectedvehicle identifier. The trigger condition is any event upon which acollection of data from the test vehicle is specified. At the occurrenceof the trigger condition the selected vehicle collects specified data tobe stored at the vehicle for future upload, or sent via a wirelessconnection to a remote center.

In one embodiment, trigger conditions include but are not limited to:number of ignition cycles, oil life, odometer readings, specific timeand date, expired amount of time, GPS location, a user initiated callrequest, and the like. In one embodiment, the client can select atrigger condition to be associated with the selected vehicle identifierfrom a list of pre-set trigger conditions. In another embodiment, theclient may create new trigger conditions or combination of triggerconditions. The client selects specific trigger conditions and activatesand deactivates these selected trigger conditions for the associatedvehicle identifier as needed through the interface.

At step 1050 the client sets parameters for the selected triggercondition on the associated test vehicle identifier. For example, aclient can select for an odometer reading trigger condition to betriggered at the first one thousand miles. In another embodiment, theclient can change the parameters of the trigger condition as needed. Forexample, a client can select for an odometer reading trigger conditionto be triggered at a specific reading of the client's specification suchas for example every five hundred miles, or every one hundred milesafter the initial trigger event. In one embodiment, there is oneparameter for the trigger condition.

The trigger condition is a uniquely occurring event in the test vehiclesuch as the first one thousand miles traveled, or a repetitive event,such as every one hundred miles traveled. In another embodiment, theparameters on the trigger conditions involve an initial thresholdtrigger parameter and a post-threshold trigger parameter. An initialthreshold trigger condition is a trigger condition that occurs once atthe selected test vehicle. A post-threshold condition is a triggercondition that occurs after an initial trigger condition has occurred atthe selected test vehicle.

At step 1060 the client selects the type of vehicle data parameters tobe collected at the occurrence of the trigger condition at the testvehicle. The client associates the type of vehicle data parameters to becollected with the selected vehicle or group of vehicles based on theselected vehicles' vehicle identifier. Types of vehicle data parameterscan be selected from any information that can be gathered about the testvehicle. In one embodiment, the client selects the type of vehicle dataparameters to be collected from pre-available data types. A list or agroup of vehicle data types that can be collected at the vehicle is madeavailable to the client for selection. In another embodiment, the clientcreates a new vehicle data parameter type to be collected at theoccurrence of the trigger condition. In an embodiment, the clientchooses all data parameters to be collected at the trigger conditionfrom pre-available vehicle data parameter types and newly createdvehicle data parameter types.

At step 1070 the client chooses how to apply the created triggercondition configuration. In an embodiment, the client can select betweenapplying the created trigger condition configuration to a single testvehicle, a group of test vehicles, or to save the selected configurationfor further use. The client selects the test vehicles to apply thecreated trigger condition configuration based on the vehicles'associated vehicle identifiers. The client establishes the triggercondition and the associated vehicle data type to be collected for theselected vehicle identifier. In an embodiment, the configuration issaved as a template for an individual test vehicle, a group of testvehicles, or for an entire captured test fleet. The newly createdtrigger condition configuration is saved for further use.

At step 1080 the new data capture configuration is transmitted andstored at the at least one test vehicle as described with reference toFIGS. 1-3 and FIGS. 6-8.

The method stops at step 1090.

FIG. 11 is an example of a web-enabled client interface for data captureconfiguration for a test vehicle in a captured vehicle fleet inaccordance with an embodiment of the present invention.

Web interface 1100 is any set of interactive windows, frames, computermediums, or web pages through which a client configures test vehicledata capture.

A client views and selects at least one list of test vehicles usingvehicle list interface 1110. A list of vehicle identifier associatedinformation is displayed on the vehicle list interface. A list ofvehicle identifier associated information is displayed from a capturedtest fleet database such as database 276. In one embodiment, theassociated vehicle identifiers include a vehicle identification number(VIN), a make and model of a vehicle, an odometer indicator reading, apercentage of oil life left before a next recommended oil change, and adiagnostic trouble code (DTC). In another embodiment, the list ofassociated information includes all available data parameters stored ina database about the test vehicles. The associated information is usedas test vehicle associated identifiers. The vehicle list interface 1110allows a client to change the type of data collected and the type oftrigger events that initiate data collection on a test vehicle. In anembodiment, the client can access and view vehicle informationassociated with test vehicles in a captured test fleet.

Using active trigger interface 1120, a client views and selects whichtrigger conditions are activated for the selected test vehicle or groupof vehicles. In one embodiment, triggers are threshold conditions orevents at the occurrence of which data is collected about an associatedtest vehicle. In an embodiment, the types of triggers are standardizedto be the same for all vehicles in a captured test fleet. In anotherembodiment, triggers are created separately for each different vehicleor group of vehicles in a captured test fleet. In another embodiment,the client creates new triggers to be associated with the vehicleidentifiers. Trigger conditions include, but are not limited to numberof ignition cycles, time and date, oil life, odometer readings, specifictime, expired amount of time, a request for continuous operation, a userinitiated call request, GPS location, and the like. The various triggerconditions can be set to be active or inactive based on the selection ofa client. The selected trigger conditions are associated with theselected test vehicle identifier in the provided database. In oneembodiment, each trigger is configured with an expiration event. Anexpiration event is any event to terminate the functioning of thetrigger, such as, for example, a predetermined calendar date, apredetermined span of time following a first ignition cycle, apredetermined mileage, an occurrence of a first service visit, leavingor entering a predetermined geographical location as determined by GPS,a predetermined internal bus message, application of a predeterminednumber of braking cycles, a predetermined number of acceleration events,a predetermined number of applications of a door lock, a predeterminednumber of applications of a window event, application of a predeterminednumber of vehicle output events.

In another embodiment, each trigger is associated with at least onepermission instruction. A permission instruction grants access to aspecified person or group of people. In another embodiment, access to atrigger includes the ability to create, modify or terminate the trigger.In another embodiment, access to a trigger includes access to data andparameters collected by the trigger. In one embodiment, permissioninstructions are controlled with a password. In one embodiment, creationof the trigger results in ownership of the trigger including access andthe ability to grant access to other specified persons.

Permission instructions apply to vehicle and vehicle configurations. Forexample, a user creates one or more triggers and assigns permissions tosaid triggers. For example, if a user creates a trigger for a specificvehicle, then the user assigns a permission value allowing other usersto utilize the specific vehicle. The other users are able to use theexisting triggers within the vehicle telematics unit, modify theexisting triggers, or create new triggers, depending on the levels ofpermissions granted. Permissions may also apply to parameter retrievaldefinitions. Multiple users may access the same vehicle. In oneembodiment, modifications to a trigger or parameter are associated withthe user that made the modification so that a history is created.

The threshold of a specific trigger event is set using a triggersettings interface 1130. In an embodiment, a trigger settings interface1130 is associated with each selected or newly created trigger. In oneembodiment, each trigger threshold is individually controllable. In theembodiment shown, a client sets odometer trigger thresholds in thetrigger settings interface 1130. In one embodiment, an initial triggerthreshold and a post-threshold trigger can be set in the triggersettings interface 1130. An initial trigger threshold is a firstoccurring trigger condition such as when a test vehicle's odometer firstindicates a set distance. A post-threshold trigger is any conditionoccurring after the initial trigger condition and which is predicted tooccur at least once after the initial trigger condition has occurred.The client selects and establishes thresholds for selected triggerconditions. The thresholds for the trigger conditions determine when thetrigger condition occurs, and are associated with the selected testvehicles' identifiers. In an embodiment, the client selects the triggerthresholds for each selected trigger condition to be associated with theselected vehicle identifiers.

A client selects the type of data that is collected from an at least onetest vehicle at the occurrence of a trigger event at a data collectionsettings interface 1140. Types of data parameters collected are selectedfrom any information that can be gathered about the at least one testvehicle. The data parameters that the client sets to be collected areassociated with the selected test vehicle identifier. In one embodiment,the client selects the type of data to be collected from a list ofpreset available vehicle data parameters. In another embodiment, theclient creates new data parameters to be collected at the at least onetest vehicle at the occurrence of a specific trigger event. In anotherembodiment, the client selects vehicle data parameters for collectionfrom preset available data parameters and newly created data parameters.In an embodiment, data collection settings interface 1140 specifies thetype of data and the exact vehicle data parameter collected at theoccurrence of a specific trigger event. The selected vehicle dataparameters to be collected at the occurrence of the associated triggercondition are associated with an at least one selected test vehicleidentifier.

Any activated or in-activated trigger conditions and any modifiedtrigger condition settings that were changed or set in interfaces 1120,1130, or 1140 are confirmed using a confirmation interface 1150. In oneembodiment, confirmation interface 1150 displays a summary of thechanges made by the client in interfaces 1120, 1130, and 1140. Theclient then confirms or rejects the changes. In another embodiment, theclient confirms each change separately. In another embodiment, theclient confirms all changes made in interfaces 1120, 1130, or 1140 atthe same time.

The client chooses how to apply the created trigger conditionconfiguration. In one embodiment, the client applies the created triggercondition configuration to only one test vehicle. In another embodiment,the client saves the configuration as a template to be applied to agroup of test vehicles, or to an entire captured test fleet. The createdtrigger condition configuration is associated with the selected testvehicles' vehicle identifiers. The new configuration is saved at theconfirmation interface 1150. In one embodiment, the new triggerconfiguration is stored for further use. In another embodiment, the newtrigger configuration is transmitted and stored at the at least one testvehicle as described with reference to FIGS. 1-3 and FIGS. 6-8.

In one embodiment, the web-enabled client interface for data captureconfiguration is implemented using the Java computer language. Inanother embodiment, the web-enabled client interface is implemented in ahardware-neutral computer language. In one embodiment, the web-enabledclient interface for data capture configuration is implemented using C#.In another embodiment, the application for the web-enabled clientinterface is a stand-alone application. In yet another embodiment, theweb-enabled client interface is configured to provide direct access tothe controls for vehicle triggers and data collection.

It is anticipated that the invention will be embodied in other specificforms not described that do not depart from its spirit or essentialcharacteristics. The described embodiments are to be considered in allrespects only as illustrative and not restrictive.

We claim:
 1. A data-collection tool for configuring atelematics-equipped vehicle to collect vehicle data remotely viawireless communication with a telematics unit of the vehicle,comprising: a client computer having stored thereon a client interfaceprogram, wherein upon execution by the client computer, the clientinterface program provides: a vehicle list interface through which auser can select one or more vehicles for configuration; a triggerinterface that provides access to defined triggers that can be set onthe vehicle, wherein each trigger is associated with one or more triggerconditions and one or more data items such that upon occurrence of thetrigger condition, the one or more data items are obtained andtransmitted from the vehicle; a trigger settings interface that enablesconfiguration of the one or more trigger conditions for a particular oneof the triggers; and a data collection settings interface that enablesselection of the one or more data items to be obtained upon occurrenceof a particular one of the triggers.
 2. A data collection tool asdefined in claim 1, wherein the trigger interface enables creation ofnew triggers or selection of existing triggers.
 3. A data collectiontool as defined in claim 1, wherein the client interface program enablesconfiguration of permissions instructions for one or more of thetriggers so that access to defined triggers can be restricted to certainindividuals or groups of individuals.
 4. A data collection tool asdefined in claim 1, wherein the data collections settings interfaceprovides a list of pre-available vehicle data parameters.
 5. Adata-collection system for configuring a telematics-equipped vehicle tocollect vehicle data remotely via wireless communication with atelematics unit of the vehicle, comprising: a vehicle having aninstalled telematics unit; a central facility that communicates with thetelematics unit via a wireless carrier system; and a client interfacethat enables configuration of data collection, said client interfaceproviding a number of different user input screens that together enableconfiguration of triggers, the user input screens including a firstscreen for identification of one or more vehicles to receive a trigger,a second screen that enables selection and configuration of one or moretriggers, and at least one additional screen that enables configurationof trigger conditions and data items for a particular trigger, such thata configured trigger includes at least one trigger condition and atleast one associated data item; wherein the configured trigger isdownloaded to the vehicle and, upon occurrence of the trigger condition,the data items are collected at the vehicle and uploaded from thetelematics unit to a central facility.
 6. A data collection system asdefined in claim 5, wherein the at least one additional screen includesa third user input screen that enables configuration of triggerconditions for a specified trigger, and a fourth user input screen thatenables selection of one or more data items to be associated with thespecified trigger.
 7. A data collection system as defined in claim 5,wherein the client interface includes a screen that enables a configuredtrigger to be applied to a vehicle or group of vehicles, or saved as adefined trigger for subsequent use.